Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2025

This PR contains the following updates:

Package Change Age Confidence Type Update
@eslint/js (source) 9.29.0 -> 9.30.1 age confidence devDependencies minor
@types/node (source) 22.15.32 -> 22.16.0 age confidence devDependencies minor
actions/checkout v4 -> v4.2.2 age confidence action minor
actions/github-script v7 -> v7.0.1 age confidence action patch
actions/setup-node v4 -> v4.4.0 age confidence action minor
eslint-plugin-prettier 5.5.0 -> 5.5.1 age confidence devDependencies patch
eslint-plugin-sonarjs (source) 3.0.3 -> 3.0.4 age confidence devDependencies patch
node (source) 22.16.0 -> 22.17.0 age confidence minor
prettier (source) 3.6.0 -> 3.6.2 age confidence devDependencies patch
zod (source) 3.25.67 -> 3.25.75 age confidence dependencies patch
zod (source) 3.25.74 -> 3.25.75 age confidence dependencies patch

Release Notes

eslint/eslint (@​eslint/js)

v9.30.1

Compare Source

v9.30.0

Compare Source

actions/checkout (actions/checkout)

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.7

Compare Source

v4.1.6

Compare Source

v4.1.5

Compare Source

v4.1.4

Compare Source

v4.1.3

Compare Source

v4.1.2

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

actions/github-script (actions/github-script)

v7.0.1

Compare Source

What's Changed

Full Changelog: actions/github-script@v7.0.0...v7.0.1

actions/setup-node (actions/setup-node)

v4.4.0

Compare Source

What's Changed
Bug fixes:
Enhancement:
Dependency update:
New Contributors

Full Changelogactions/setup-node@v4...v4.4.0

v4.3.0

Compare Source

What's Changed

Dependency updates

New Contributors

Full Changelog: actions/setup-node@v4...v4.3.0

v4.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-node@v4...v4.2.0

v4.1.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.1.0

v4.0.4

Compare Source

What's Changed
Documentation changes:
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.4

v4.0.3

Compare Source

What's Changed

Bug fixes:
Documentation changes:
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v4...v4.0.3

v4.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.1

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.5.1

Compare Source

Patch Changes
SonarSource/SonarJS (eslint-plugin-sonarjs)

v3.0.4

Compare Source

nodejs/node (node)

v22.17.0: 2025-06-24, Version 22.17.0 'Jod' (LTS), @​aduh95

Compare Source

Notable Changes
⚠️ Deprecations
Instantiating node:http classes without new

Constructing classes like IncomingMessage or ServerResponse without the new
keyword is now discouraged. This clarifies API expectations and aligns with standard
JavaScript behavior. It may warn or error in future versions.

Contributed by Yagiz Nizipli in #​58518.

options.shell = "" in node:child_process

Using an empty string for shell previously had undefined behavior. This change
encourages explicit choices (e.g., shell: true or a shell path) and avoids
relying on implementation quirks.

Contributed by Antoine du Hamel and Renegade334 #​58564.

HTTP/2 priority signaling

The HTTP/2 prioritization API (e.g., stream.priority) is now deprecated due to
poor real-world support. Applications should avoid using priority hints and expect future removal.

Contributed by Matteo Collina and Antoine du Hamel #​58313.

✅ Features graduated to stable
assert.partialDeepStrictEqual()

This method compares only a subset of properties in deep object comparisons,
useful for flexible test assertions. Its stabilization means it's now safe for
general use and won't change unexpectedly in future releases.

Contributed by Ruben Bridgewater in #​57370.

Miscellaneous
  • dirent.parentPath
  • filehandle.readableWebStream()
  • fs.glob()
  • fs.openAsBlob()
  • node:readline/promises
  • port.hasRef()
  • readable.compose()
  • readable.iterator()
  • readable.readableAborted
  • readable.readableDidRead
  • Duplex.fromWeb()
  • Duplex.toWeb()
  • Readable.fromWeb()
  • Readable.isDisturbed()
  • Readable.toWeb()
  • stream.isErrored()
  • stream.isReadable()
  • URL.createObjectURL()
  • URL.revokeObjectURL()
  • v8.setHeapSnapshotNearHeapLimit()
  • Writable.fromWeb()
  • Writable.toWeb()
  • writable.writableAborted
  • Startup Snapshot API
  • ERR_INPUT_TYPE_NOT_ALLOWED
  • ERR_UNKNOWN_FILE_EXTENSION
  • ERR_UNKNOWN_MODULE_FORMAT
  • ERR_USE_AFTER_CLOSE

Contributed by James M Snell in
#​57513 and
#​58541.

Semver-minor features
🔧 fs.FileHandle.readableWebStream gets autoClose option

This gives developers explicit control over whether the file descriptor should
be closed when the stream ends. Helps avoid subtle resource leaks.

Contributed by James M Snell in #​58548.

🔧 fs.Dir now supports explicit resource management

This improves ergonomics around async iteration of directories. Developers can
now manually control when a directory is closed using .close() or with Symbol.asyncDispose.

Contributed by Antoine du Hamel in #​58206.

📊 http2 gains diagnostics channel: http2.server.stream.finish

Adds observability support for when a stream finishes. Useful for logging,
monitoring, and debugging HTTP/2 behavior without patching internals.

Contributed by Darshan Sen in #​58560.

🔐 Permissions: implicit allow-fs-read to entrypoint

Node.js permissions model now allows read access to the entry file by default.
It makes running permission-restricted apps smoother while preserving security.

Contributed by Rafael Gonzaga in #​58579.

🎨 util.styleText() adds 'none' style

This lets developers remove styling cleanly without hacks. Useful for overriding
inherited terminal styles when composing styled strings.

Contributed by James M Snell in #​58437.

🧑‍💻 Community updates
Commits

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Jul 8, 2025
@renovate renovate bot enabled auto-merge (squash) July 8, 2025 07:45
@renovate renovate bot added the renovate label Jul 8, 2025
@github-actions
Copy link

github-actions bot commented Jul 8, 2025

The recent changes focus on updating dependencies, including GitHub Actions and various Node.js packages, which contribute to improved security and performance. The Node.js version used for the workflows has been bumped, ensuring better compatibility and features for the ongoing development. These updates aim to maintain the quality and reliability of the codebase during development and deployment processes.

Walkthrough

  • Chore: Updated GitHub Actions dependencies in workflow files for enhanced performance and security.
  • Chore: Upgraded several npm packages in package.json and package-lock.json, reflecting minor improvements and patches.
  • Refactor: Incremented Node.js version from 22.16.0 to 22.17.0 for better feature support and compatibility.
  • Chore: Updated package versions (e.g., zod, eslint, and prettier) to maintain alignment with latest minor versions.

Model: gpt-4o | Prompt Tokens: 4044 | Completion Tokens: 184

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check out this supportive analysis of your code, enhanced with AI guidance. It includes predictions that aren't absolute, so embrace what benefits you most. Ultimately, your choices drive the process—AI it's here to aid your development.
Model: gpt-4o | Prompt Tokens: 5451 | Completion Tokens: 563

runs-on: [ubuntu-latest]
steps:
- uses: actions/github-script@v7
- uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using specific commit hashes for actions provides more certainty over the version being used, avoiding unexpected changes due to updates. It's a good practice to update to the latest tagged version regularly which offers stability improvements and new features. Consider using the latest available tag if no specific functionality requires sticking to a particular commit hash.

Comment on lines 21 to 24
- name: Checkout source branch
uses: actions/checkout@v4
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
ref: ${{ env.SOURCE_BRANCH }}
path: source-folder
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifying a commit hash for actions checkout and setup-node ensures a specific version is used, reducing unexpected changes but requires regular updates. Consider reviewing and updating the hash periodically to leverage improvements and enhancements in actions. Moreover, ensure these updates are verified against your workflow requirements.

Comment on lines 21 to 26
- name: Checkout source branch
uses: actions/checkout@v4
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
- name: Setup Node
uses: actions/setup-node@v4
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
with:
node-version: 18
cache: npm
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to the build workflow, specifying commit hashes for actions can ensure consistency. However, regular updates to the specified hashes should be done to benefit from bug fixes and improvements. Test thoroughly after each update to ensure compatibility with existing workflows.

Comment on lines -22 to 25
"parse-diff": "0.11.1",
"zod": "3.25.74",
"zod": "3.25.75",
"zod-to-json-schema": "3.24.6"
},
"devDependencies": {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency updates appear to be minor versions, indicating backward-compatible changes. Ensure that any breaking changes are accounted for in your codebase. Regularly test your code against updated dependencies to catch any potential issues introduced by these updates.

@@ -1 +1 @@
22.16.0
22.17.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node.js version bump from 22.16.0 to 22.17.0 should be verified against existing code to ensure compatibility. Minor version updates might include performance improvements or bug fixes. Always check the Node.js release notes for any potentially impactful changes.

Comment on lines -21 to 28
"parse-diff": "0.11.1",
"zod": "3.25.67"
"zod": "3.25.75"
},
"devDependencies": {
"@eslint/js": "9.29.0",
"@types/node": "22.15.32",
"@eslint/js": "9.30.1",
"@types/node": "22.16.0",
"@typescript-eslint/eslint-plugin": "7.18.0",
"@typescript-eslint/parser": "7.18.0",
"@vercel/ncc": "0.38.3",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating dependencies to their latest versions is a good practice to ensure you have the latest features and security updates. Test your application thoroughly after dependency updates to identify any incompatibilities or changes that might affect your application behavior.

@renovate renovate bot force-pushed the renovate/non-major-dependencies branch from ca400c0 to e930af5 Compare July 8, 2025 07:47
@renovate renovate bot merged commit 40cde57 into main Jul 8, 2025
8 checks passed
@renovate renovate bot deleted the renovate/non-major-dependencies branch July 8, 2025 07:48
@github-actions
Copy link

github-actions bot commented Jul 8, 2025

This change primarily focuses on upgrading dependencies and updating GitHub workflow actions to use more specific commit hashes, aiming to improve stability and security. Key npm dependencies were updated to newer versions, improving compatibility and possibly fixing known issues. The update to explicit action commit hashes increases the reliability of the CI/CD process by preventing unintended changes due to updates in action versions.

Walkthrough

  • Refactor: GitHub workflow actions have been updated to use specific commit hashes instead of version tags, ensuring stability and security in automated processes.
  • Chore: Upgrades of several npm package dependencies in package.json files, such as updating zod, eslint, and prettier, ensuring they're at recent stable versions.
  • Test: Node version updated in the pr-summary to improve testing and compatibility across environments.

Model: gpt-4o | Prompt Tokens: 4291 | Completion Tokens: 168 | Diff Range: ca400c0...e930af5

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've provided a supportive analysis of your code with AI assistance. Remember, AI offers predictions, not absolute truths, so choose what suits your needs best. It's your expertise that takes the lead, while AI offers guidance in the background.
Model: gpt-4o | Prompt Tokens: 2122 | Completion Tokens: 423 | Diff Range: ca400c0...e930af5

Comment on lines -17 to 20
steps:
- uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7
- uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
with:
script: |
github.rest.git.deleteRef({
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a minor update in the version specification of the GitHub Action. The comment next to the action version should correspond to the actual tag you're using. Ensure the version numbers are always aligned. Consider automation to manage these updates.

Comment on lines 18 to 24
if: ${{ !startsWith(github.head_ref || github.ref_name, 'release/') }}
steps:
- name: Checkout source branch
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
ref: ${{ env.SOURCE_BRANCH }}
path: source-folder
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When modifying version numbers for actions, ensure comments accurately reflect these versions to avoid confusion. This helps maintain consistency and transparency in the workflow configuration.

Comment on lines -31 to 34
- name: Setup Node (PR Summary)
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
with:
node-version-file: source-folder/pr-summary/.node-version
cache: npm
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears npm prune --omit=dev is used. If this command is run automatically after the setup, consider running it explicitly as a separate step to ensure clarity and manageability in your workflow.

Comment on lines 18 to 25
path: [pr-summary, pr-review]
steps:
- name: Checkout source branch
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
- name: Setup Node
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
with:
node-version: 18
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The paths pr-summary and pr-review should be relative to the repository's root, make sure they are correct as they affect the checkout operation. Validating paths ensures your workflow steps target the correct directories.

Comment on lines 41 to 49
path: [pr-summary, pr-review]
steps:
- name: Checkout source branch
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
- name: Setup Node
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
with:
node-version: 18
cache: npm
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just like other occurrences, make sure comments and versions remain aligned to simplify version tracking. Consistency in documentation helps in maintaining the workflow over time.

github-actions bot pushed a commit that referenced this pull request Jul 8, 2025
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant